An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program.(c) You cannot use another developer’s icon, brand, or product name in your app’s icon or name, without approval from the developer. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

Hello everyone, I’m experiencing an issue with the review process for my app on App Store Connect. My app has been stuck in “Waiting for Review” for over 30 days, and the review process has not started yet. Initially, I submitted the build on February 9, but the status remained “Waiting for Review” for a long time and never moved to “In Review.” Because of this, I canceled the submission and resubmitted the build on February 17. However, even after resubmitting, the app is still stuck in “Waiting for Review.” I also submitted a request for an expedited review, but unfortunately I have not received any response regarding that request either. Since the app status is still “Waiting for Review,” the Resolution Center option is not available yet, so I cannot contact the App Review team directly from there. I also attempted to contact Apple Developer Support but have not received a response yet. Has anyone experienced a similar situation where the app remained in “Waiting for Review” for this long? Any guidance or suggestions on how to move the review process forward would be greatly appreciated. App details: App ID: id6755089083 First Submission Date: February 9 Resubmission Date: February 17 Submission ID: bbad192f-768f-40f6-bcc3-47f30b5ecb6d Thank you for your help.

Hello, I submitted my app for review for the first time about two weeks ago and it is still stuck in "Waiting for Review" with no update. I haven't received any feedback yet and I'm not sure if this kind of delay is normal or if something might be wrong. Has anyone experienced something similar? What did you do in this situation? Thanks.

Hello everyone, My app has been in "Waiting for Review" status since February 20, and it still hasn’t moved to the review stage yet. On March 9, I submitted a support ticket asking whether there might be any issue with my submission or if additional information is required from my side. However, I have not received any response from Apple so far. At this point, I’m not sure if I should continue waiting or if there is anything else I should do to resolve the situation. App ID: 6759365919 Ticket ID: 102839874589 If anyone has experienced a similar situation or if an Apple staff member could help check the status, I would really appreciate it. Thank you very much.

Hello everyone, I submitted my app USDT Miner – Rig Manager to App Store Connect on February 2, and it has been in “Waiting for Review” status since then. I understand that review times can vary, but it has now been several days without any status change or feedback. This is my first submission for this app, and there are no resolution center messages or rejection notices so far. I wanted to ask: Is this delay normal at the moment? Are there any known review backlogs or factors that could cause an extended “Waiting for Review” status? Is there anything recommended to do from the developer side, or should I simply continue waiting? Any insights from Apple staff or fellow developers who’ve experienced similar delays would be appreciated. Thank you.

Hi everyone, I’m using StoreKit 2 with .storeButton(.visible, for: .policies) inside my SubscriptionStoreView. The buttons appear correctly, but when tapped, a sheet opens that says “Terms of Service Unavailable” or “Something went wrong. Try again.” I’ve already added the required URLs (Privacy Policy and Terms of Use) in App Store Connect under App Information, but they still don’t show in the sheet. Does anyone know how this is supposed to work? • Are the URLs pulled directly from App Store Connect? • Do they only appear correctly in production? • Or do we need to manually set them in code for testing/TestFlight? Any insight would be greatly appreciated — just want to make sure everything is in place before submitting for review. Thanks!

My app (Markets: Global Trading 24/7, App ID: 6756673679) has been in "In Review" status since March 10, 2026 at 9:38 AM ET. Prior to that, it was in "Waiting for Review" for approximately 4-5 days after submission on March 5. It appears that the demo account we had provided was used to log into the app shortly after the status changed to "In Review" on March 10, but no additional activity since then. I submitted a support ticket via App Store Connect on March 12 and received an automated acknowledgment but no further response. Is this delay expected, or is there something I should do?

Hi, I submitted my iOS app for review on Wednesday, March 4th (around 4 PM UTC+8), and it has been stuck in "Waiting for Review" for over 7 business days with no progress. I have already submitted an Expedited Review request 2 days ago, but the status remains unchanged. I understand review times can vary, but this extended wait with no movement or communication is making it difficult to plan our launch timeline. Has anyone experienced a similar delay recently? Is there anything else I can do at this point? Any insight would be greatly appreciated. Thank you.

Hello everyone, I am desperately seeking guidance. My app has been stuck in the "Waiting for Review" status for over 17 days (since at least Feb 13). It hasn't even entered the "In Review" stage. I completely understand that review times can vary, but what's concerning is that we seem to be caught in a system loop. We have proactively contacted Apple Developer Support multiple times over the past few weeks. Specifically, we have open cases (Case ID: 102820493078 and Case ID: 102820491288) with messages sent on: Feb 13 Feb 18 Feb 23 Feb 24/25 Unfortunately, we have only received generic automated responses, and the status remains firmly stuck at "Waiting for Review". At this point, we are extremely worried that our binary might be caught in a system glitch or ghosted in the queue. Could any Apple Staff here kindly look into these Case IDs to see if there is a technical issue preventing our app from entering the review queue? Has any other developer experienced a similar >17 days wait time just to enter the queue recently? Any help to untangle this would be greatly appreciated. Thank you!

I have app update that’s been waiting for review since 4th February. I’ve raised a case, posted to the case a few times, been told twice by support that I ‘haven’t been forgotten’ and yet nothing changes and no useful communication. It’s an update to an existing published app. I have other apps waiting for review and TestFlight approval for almost as long. Now approaching 10% of my year’s developer subscription has already been spent just waiting. What‘s the answer here? I am reticent to reject and resubmit As there’s no evidence that that would make any difference. None of the app updates I’ve submitted for other apps after this one have been reviewed either.

I’ve been developing apps for 8 years. On the tenth update of my latest app, I got yet another new rejection reason. I co-founded an app called Yuna AI with my wife, who is a Registered Dietitian and a member of the CDO. When trying to release version 1.0.10, I was told I can’t publish it under my name as a sole proprietor. I’m honestly starting to lose faith in the review process. My previous submission was rejected for not properly disclosing in-app purchases, even though my app doesn’t have any in-app purchases. Rejection reason "The app must be published under a seller and company name that is associated with the organization or company providing the services. In this case, the app must be published under a seller name and company name that reflects the Yuna AI name. The guideline 5.1.1(ix) requirements give users confidence that apps operating in highly regulated fields or that require sensitive user information are qualified to provide these services and will responsibly manage their data." Do i really have to pay to incorporate a company to put my app under and a sole proprietorship isn't enough? Im going to be moving soon and probably not best for me to incorporate now in Canada. does that mean i don't get to update my app anymore?

My app has been under review for longer than usual, and I would like to check if anyone else is experiencing the same situation. Submitted Date: Tuesday at 11:37 AM Apple ID: 6499260089 It has been more than 3 days now and the status is still “Waiting for Review” / “In Review.”

a I am submitting this appeal because we believe our app was misunderstood and the review outcome and follow-up communication have been unfair and mechanically handled. 1) What happened / Outcome we disagree with Our submission was rejected under Guideline 4.8 – Design – Login Services, with the reviewer stating that our app uses a third-party login service but does not provide an equivalent login option that meets Apple’s requirements (limited data collection, private email option, no advertising tracking without consent). However, our game does not require or force any third-party login. The feature being treated as “login” is not a login service at all—it is Mainland China real-name / anti-addiction compliance verification. 2) Why we believe we comply with the App Review Guidelines A. The feature in question is compliance verification, not login Players do not need to create or log into any in-game account to play. The flow exists solely to satisfy Mainland China real-name/anti-addiction compliance requirements. Verification can be completed by either: Using TapTap only as a real-name verification authorization option, or Manually entering a Chinese ID number + legal name to pass verification and play. Because this is verification, not an account login, Guideline 4.8 “Login Services” should not apply in the way the rejection message assumes. B. There is no “playable account” to provide After we clarified the above, we continued to receive repeated, template-like requests to provide a “playable account.” This request does not match our product design: there is no account system required for gameplay, so there is no “review account” to provide. We have already provided the information needed to complete the verification path (ID + name for the compliance flow), yet the responses remained repetitive and did not reflect that the reviewer checked our explanation. 3) Why we believe the handling was unfair Even after clearly explaining that this is not a login system, the review communication continued with mechanical responses that did not address the clarification. This caused significant delays to our release timeline and appears to be unfair treatment compared with many existing App Store apps that use similar compliance verification flows. 4) What we are requesting from the Appeals Team Please investigate and correct the misclassification of our real-name compliance verification as a “login service” under Guideline 4.8. If the team still believes Guideline 4.8 applies, please provide: The specific guideline rationale, and The exact screen/step in our app that is being interpreted as “login.” Please advise what specific materials you need to proceed efficiently (e.g., screen recording of the verification flow, step-by-step review instructions, configuration notes). We are ready to provide them immediately.

Hello, My app TouCal: AI Calorie Tracker seems to be stuck in the App Review process and I’m trying to understand if something might be wrong with the submission. App ID (Apple ID): 6698870692 Timeline: First submission: March 9 Since then the app has been in “Waiting for Review” for 4 days (as of March 13) Normally my app reviews are approved within 1–2 days, so this delay seems unusual. Please help review this submission as soon as possible! My users are currently facing a bug that should have been fixed in this version. Any guidance would be greatly appreciated. Thank you.

We are 25 days into "Waiting for Review" with no movement, no messages, and no Resolution Centre activity. Submitted 16 February. Apple ID: 6758049144 This is a finance category app used by regulated financial advisers in the UK. The delay is now directly affecting live paying customers operating under FCA compliance obligations. We have confirmed everything on our side is in order. This is not a metadata issue or an incomplete submission. Has anyone from the App Review team seen this? And has anyone here successfully broken a delay of this length - what actually worked?

Hello everyone, I would like to ask if other developers are currently experiencing unusually long App Review delays for new apps. Here is my timeline for this app (Apple ID: 6758083858): Jan 22, 2026: Initial build submitted Jan 22 – Mar 7, 2026: Status remained “Waiting for Review” and never entered the “In Review” stage Mar 7, 2026: Cancelled and resubmitted a new build Current status: Still “Waiting for Review” During this period, I have already tried several ways to resolve the issue: Contacted Apple Developer Support multiple times Submitted an expedited review request Sent follow-up emails regarding the delay Contacted Apple support by phone and asked them to leave a message for the App Review team Each time I was told that the situation would be checked or that the review team would look into it. However, it has now been about two weeks since my last contact and there has been no update or progress. While browsing the Developer Forums, I also noticed that many recent posts seem to describe the same situation, especially with new app submissions stuck in “Waiting for Review”. So I would like to ask: Are other developers currently experiencing similar delays? Has anyone recently seen their new app move from “Waiting for Review” to “In Review”? Could this be related to a broader App Review queue slowdown? Any recent experiences or information would be greatly appreciated. Thank you.

Hello Apple Developer community, I’m reaching out because I’m currently experiencing an unusually long delay in the App Review process. My app (App ID: 6748461479) has been stuck in “Waiting for Review” since February 23, and there has been no change of status, no approval, no rejection, and no message from the App Review team. This situation is becoming problematic because I have publication deadlines and release planning that depend on this update being reviewed and approved. According to Apple’s own information, around 90% of apps are reviewed within 24 hours. I completely understand that some cases may take longer depending on workload or additional checks, but remaining in “Waiting for Review” for several weeks without any update is quite concerning. Current situation: Status has remained “Waiting for Review” since February 26 No request for additional information The build follows the App Store Review Guidelines Previous versions of the app were approved without issues Has anyone experienced similar delays recently, or is there anything I should do in this situation? Any advice or clarification would be greatly appreciated. Best regards, An Apple Developer

Hello, I'm a first time developer and both of my submissions for NexFi - Portfolio Tracker have been suck in Waiting for Review for an extended time. TestFlight: My first build was submitted on Feb 15th (25+ days) and still Waiting for Review Production/Distribution: Submitted March 2nd (10 days) and still Waiting for Review. It is a finance category app (portfolio tracker) that requires no login, no account creation, and no server side user data so I figured it should be a relatively quick process as there is a minimal privacy footprint. App Name: NexFi - Portfolio Tracker Platform: iOS App ID: 6759226354

My app has been stuck in "Waiting for review" for longer than usual. I just wanted to check and see if there are delays or something else is going on that I can fix. Thank you.